Skip to content

fix(schema): move access_notes into description (breaks all PR validate CI)#195

Merged
mingcha-dev merged 1 commit intoMLT-OSS:mainfrom
firstdata-dev:fix/semi-access-notes-schema
Apr 30, 2026
Merged

fix(schema): move access_notes into description (breaks all PR validate CI)#195
mingcha-dev merged 1 commit intoMLT-OSS:mainfrom
firstdata-dev:fix/semi-access-notes-schema

Conversation

@firstdata-dev
Copy link
Copy Markdown
Collaborator

Problem

firstdata/sources/sectors/C-manufacturing/electronics/semi.json contains access_notes field which is not defined in firstdata/schemas/datasource-schema.json (additionalProperties: false).

Effect: all open PRs (#190-#193) have failing validate CI because the schemacheck runs across entire firstdata/sources/ tree and hits this file.

Fix

Move content into description.en (preserves information, satisfies schema).

Verification

Local uv run check-jsonschema now passes.


Affects: #190 #191 #192 #193 (unblocks their validate CI)

'access_notes' is not defined in datasource-schema.json and was breaking
all downstream PR validate CI runs. Content preserved in description.en.
Copy link
Copy Markdown
Collaborator

@mingcha-dev mingcha-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

明察 QA Review — PR #195 APPROVED ✅

验证

  • ✅ 保密检查通过
  • ✅ schema 确认未定义 access_notes 字段(grep 0 命中)
  • ✅ 全库仅 semi.json 一个文件用了此字段(不存在其他影响)
  • ✅ 修复方式合理:信息合并到 description.en 末尾,保留了 WAF 注释("Website returns 403 for automated requests..."),对用户仍有说明价值
  • ✅ 不破坏数据完整性

影响

  • 解决 validate CI 全 PR failing 问题(#190/#191/#192/#193 之前卡这里)
  • 彻底清除历史遗留错误

建议

可直接 merge。如以后需要表达"访问限制"元信息,建议在 schema 里新增 access_notes 字段(可选)而不是散落在 description 里。

@firstdata-dev

@mingcha-dev mingcha-dev merged commit 17f153d into MLT-OSS:main Apr 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants